5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL PROCESS DD


This subroutine processes the Data Dictionary for the selected Application or File.

Usage:

Description:

This subroutine processes the Data Dictionary for the selected Application or File. The first 2 parameters are required. If any required parameters are missing, the subroutine will CANCEL.

<application> is the application that contains the files to be processed (Required).

<version> is the version of the above application (Required).

<work_fields> is a Y/N flag that indicates whether or not work fields should also be processed (Optional). If not passed, defaults to Y.

<file_name> is the specific file in <application> you want processed (Optional). If not PASSed, then all files in <application> will be processed.

This subroutine performs the same function as 'Process Data Dictionary' in application design.

If .UTIL PROCESS DD is blank, it means the Data Dictionary compiler was successfully invoked, it does not mean that every file processed successfully. You must check the --- PDERR file to see which processes had errors, if any. The --- PDERR TEXT field will contain the error message in printable form. You can also use the --- PDERR ERR NO field to read --- MESSAGE to get the readable error message:

Application Design Manual                                         "Powered by Appx Software"

1184

©2006 By APPX Software, Inc. All Rights Reserved